FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.3.2.20444 HL7 v3 Value Set SecurityPolicy

Vocabulary Work Group Maturity Level: N/AExternalUse Context: Any

This value set (http://hl7.org/fhir/ValueSet/v3-SecurityPolicy) is defined as part of HL7 v3. Related FHIR content: SecurityPolicy.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-SecurityPolicy
Name:SecurityPolicy
Definition: Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive
OID:2.16.840.1.113883.1.11.20444 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is not currently used


This value set includes codes from the following code systems:

 

This expansion generated 19 Apr 2017


This value set contains 48 concepts

Expansion based on http://hl7.org/fhir/v3/ActCode version 2016-11-11

All codes from system http://hl7.org/fhir/v3/ActCode

CodeDisplayDefinition
SecurityPolicysecurity policyTypes of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
  ObligationPolicyobligation policyConveys the mandated workflow action that an information custodian, receiver, or user must perform. Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.
    ANONYanonymizeCustodian system must remove any information that could result in identifying the information subject.
    AODaccounting of disclosureCustodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested.
    AUDITauditCustodian system must monitor systems to ensure that all users are authorized to operate on information objects.
    AUDTRaudit trailCustodian system must monitor and maintain retrievable log for each user and operation on information.
    CPLYCCcomply with confidentiality codeCustodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.
    CPLYCDcomply with consent directiveCustodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
    CPLYJPPcomply with jurisdictional privacy policyCustodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
    CPLYOPPcomply with organizational privacy policyCustodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
    CPLYOSPcomply with organizational security policyCustodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
    CPLYPOLcomply with policyCustodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
    DECLASSIFYLABELdeclassify security labelCustodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
    DEIDdeidentifyCustodian system must strip information of data that would allow the identification of the source of the information or the information subject.
    DELAUdelete after useCustodian system must remove target information from access after use.
    DOWNGRDLABELdowngrade security labelCustodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
    DRIVLABELderive security labelCustodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
    ENCRYPTencryptCustodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.)
      ENCRYPTRencrypt at restCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
      ENCRYPTTencrypt in transitCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.
      ENCRYPTUencrypt in useCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user.
    HUAPRVhuman approvalCustodian system must require human review and approval for permission requested.
    LABELassign security labelCustodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes.
    MASKmaskCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret".
    MINECminimum necessaryCustodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use.
    PERSISTLABELpersist security labelCustodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.
    PRIVMARKprivacy markCustodian must create and/or maintain human readable security label tags as required by policy. Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label."
    PSEUDpseudonymizeCustodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject.
    REDACTredactCustodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.
    UPGRDLABELupgrade security labelCustodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
  RefrainPolicyrefrain policyConveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc.
    NOAUTHno disclosure without subject authorizationProhibition on disclosure without information subject's authorization.
    NOCOLLECTno collectionProhibition on collection or storage of the information.
    NODSCLCDno disclosure without consent directiveProhibition on disclosure without organizational approved patient restriction.
    NODSCLCDSno disclosure without information subject's consent directiveProhibition on disclosure without a consent directive from the information subject.
    NOINTEGRATEno integrationProhibition on Integration into other records.
    NOLISTno unlisted entity disclosureProhibition on disclosure except to entities on specific access list.
    NOMOUno disclosure without MOUProhibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
    NOORGPOLno disclosure without organizational authorizationProhibition on disclosure without organizational authorization.
    NOPATno disclosure to patient, family or caregivers without attending provider's authorizationProhibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone).
    NOPERSISTPno collection beyond purpose of useProhibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
    NORDSCLCDno redisclosure without consent directiveProhibition on redisclosure without patient consent directive.
    NORDSCLCDSno redisclosure without information subject's consent directiveProhibition on redisclosure without a consent directive from the information subject.
    NORDSCLWno disclosure without jurisdictional authorizationProhibition on disclosure without authorization under jurisdictional law.
    NORELINKno relinkingProhibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked.
    NOREUSEno reuse beyond purpose of useProhibition on use of the information beyond the purpose of use initially authorized.
    NOVIPno unauthorized VIP disclosureProhibition on disclosure except to principals with access permission to specific VIP information.
    ORCONno disclosure without originator authorizationProhibition on disclosure except as permitted by the information originator.